|
Define and prepare the test environment
| Identify which tools, operational systems and so on will support test activities. |
Define White-box and Black-box Techniques
Identify which white-box and black-box technique better fits with the interactions (paths) that will be
tested.
White-box -
Black-box -
|
Define strategy(ies) for test the integration of components and modules
Identify a strategy which meets the organizational needs. The integration os components and modules can be
performed using most-common approaches:
Top-down -
Bottom-up -
Big-bang Strategies -
Threads Integration -
|
Define the coverage criteria
| Identify features and variation points to be tested, identify features and variation points not to be tested, as
well as identify critical paths and relationships. This identification is based on requirements and use cases analysis
and priorization performed during RiPLE-RE. The SPL risk document should be considered during this step. |
Define the test input domain
| Determine the test input domain, in order to address the coverage criteria defined previously. |
Define the Pass/Fail criteria
| Specify the stop criteria to be used during the integration test cycle, e.g. 98% passed. |
Summarize the information in a test plan
| It is recommendable to use a test plan template for all the modules, so that information reuse is encouraged. |
|
